This isn't actually completed, right? There are Signals still left in the Event.elm for example.

D3.elm begins with module D3 ( -- code -- ) where now the syntax is module D3 exposing ( -- code -- )

I'm gonna take a look at this, finally. Thanks for your patience. Related to #34.

Bump!

another bump 😸

hey guys. I have spoken with Spiros ( @seliopou ) I have largely slacked off on this. Here I will outline a few choices that must be made.

First Elm offers two ways of interacting with the outside world:

• ports
• native code
  The Elm community typically prefers the first one, while Spiros' approach (written for the earlier versions of Elm) uses the second.

Once we master that, there is one more dillemma related to D3JS 4.0
Should we continue to use D3JS at all?

• Elm has great Svg and Canvas capabilities. We can reproduce all of D3's nice features combined with the strength of Elm
• We can try to write an interface into the existing D3 methods.

This is a basic summary of chats with Spiros over the summer. I don't want to speak for him. This is my pull request and admittedly it's stump.

Sorry guys been really busy lately and haven't made much progress even when I've had time to look into this. I'll make an effort to post an update to #34 sometime this week.

@seliopou let me know what I can do to help. Somewhat of an Elm n00b but may be able to assist somehow (plus it'll be fun!)

@seliopou interested in trying to pick this up - any chance you have any WIP stuff you haven't pushed yet?

If not, even some notes about where you got to and what issues you faced would be helpful.